Denormalization of healthcare data

ABSTRACT

Systems, methods, and computer-readable media for denormalizing healthcare data are provided. An indication a patient has been added to a tracking list is received. The tracking list is determined to be associated with a primed view. Data is retrieved for the patient. The data for the patient is cached into the primed view before a clinician requests the data.

BACKGROUND

The advent of powerful servers, large-scale data storage and otherinformation infrastructure has spurred the development of advanced datawarehousing. Structured query language (SQL) engines and inexpensivelarge disk arrays have for instance been harnessed in financial,scientific, medical, and other fields to capture vast streams oftransactional, experimental, and other data.

In the case of medical data management, the task of querying, receiving,conditioning, and analyzing large quantities of clinical information isparticularly challenging. The sources of medical data for anorganization, for instance, may include various hospitals, laboratories,research or other facilities, each of which may generate data records atdifferent times and in widely varying formats. Clinical systems areoften extremely large, with a high volume of data (e.g., results and/ororders), and retrieving what is necessary to meet business requirementsis inefficient. That is in part because querying the various datasources requires significant processing overhead. Queries of that dataare utilized, for example, by clinicians for each encounter with eachpatient. Each query may be made to tables having thousands of rows for apatient with many encounters. This heavy back-end processing istime-consuming and particularly burdensome to the server and networkinfrastructure, as well as to the clinician.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter. The present invention is defined by the claims.

In brief and at a high level, this disclosure describes, among otherthings, methods, systems, and computer storage media for denormalizationof healthcare data. An indication a patient has been added to a trackinglist is received. The tracking list is determined to be associated witha primed view. Data is received for the patient. The data for thepatient is cached into the primed view before a clinician requests thedata.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is described in detail below with reference to theattached drawings figures, wherein:

FIG. 1 is a block diagram of an exemplary computing system suitable foruse in implementing embodiments of the present invention;

FIG. 2 schematically shows a network environment suitable for performingembodiments of the invention;

FIG. 3 is a flow diagram showing a method for denormalizing healthcaredata, in accordance with an embodiment of the present invention; and

FIG. 4 is a flow diagram showing a method for denormalizing healthcaredata, in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION

The subject matter of the present invention is described withspecificity herein to meet statutory requirements. However, thedescription itself is not intended to limit the scope of this patent.Rather, the inventors have contemplated that the claimed subject mattermight also be embodied in other ways, to include different steps orcombinations of steps similar to the ones described in this document, inconjunction with other present or future technologies. Moreover,although the terms “step” and/or “block” may be used herein to connotedifferent components of methods employed, the terms should not beinterpreted as implying any particular order among or between varioussteps herein disclosed unless and except when the order of individualsteps is explicitly described.

A primed view refers to a preloaded set of data of a specific entitytype loaded for a population of patients. Each patient in the populationhas a row of data for each encounter if the encounter has qualifyingdata. The data is loaded prior to a user requesting the data. Securityand privileges of the proxy personnel on the view restricts what data isloaded into the primed view. This typically reflects the securitysettings of users with the broadest access that will leverage aparticular primed view. Proxy personnel with access to facilities arebased on the broadest groups of facilities users have access to. Proxypersonnel may have a position with access privileges inclusive of allusers that will share the primed view. Security and privileges of theuser accessing a primed view restricts what data is read from the primedview for a particular user. If the user has access to more facilitiesthan the proxy personnel or additional privileges, the additionalinformation is not visible from the primed view. A primed view usergroup is utilized to determine what users can access a given primedview. Each user may be assigned to one or more primed view user groups.Only users assigned to the group associated to the primed view mayutilize the primed view.

Embodiments of the present invention can improve performance of dataretrieval and quickly display the data to end users. Embodiments presentadvantages over other systems by executing discrete queries andpreparing the information to retrieve and display before the userrequests it.

Accordingly, one embodiment of the present invention is directed to oneor more computer hardware storage media storing computer-useableinstructions that, when used by one or more computing devices, cause theone or more computing devices to perform a method of facilitatingselective denormalization of healthcare data. The method includesreceiving an indication a patient has been added to a tracking list. Thetracking list is determined to be part of a primed view. Data isreceived for the patient. The data for the patient is cached into theprimed view.

Another embodiment of the present invention is directed to one or morecomputer hardware storage media storing computer-useable instructionsthat, when used by one or more computing devices, cause the one or morecomputing devices to perform a method of facilitating selectivedenormalization of healthcare data. A tracking list of patients isprepared based on a schedule of appointments. Data for each patient inthe tracking list is retrieved. The data may be limited in time andselected based on a condition associated with the patients, a roleassociated with a clinician, and/or a unit associated with a healthcarefacility. The data is cached into a primed view. The primed view may beavailable to the clinician without the clinician requesting the data. Anindication updated data is available for one or more patients isreceived. The data is refreshed with the updated data in the primedview.

Yet another embodiment of the present invention includes a system forfacilitating selective denormalization of healthcare data. The systemincludes one or more processors coupled to a computer hardware storagemedium, the computer hardware storage medium having stored thereon aplurality of computer software components executable by the processor.The computer software components include a tracking component thatreceives an indication a patient has been added to a tracking list. Aretrieval component retrieves data for each patient in the trackinglist. The data may be limited in time and selected based on a conditionassociated with the patients, a role associated with a clinician, and/ora unit associated with a healthcare facility. A cache component cachesthe data into a primed view. The primed view may be provided before auser initiates a query. A refresh component retrieves updated data andrefreshes the data with the updated data in the primed view.

Having briefly described embodiments of the present invention, anexemplary operating environment suitable for use in implementingembodiments of the present invention is described below. Referring toFIG. 1 an exemplary computing environment with which embodiments of thepresent invention may be implemented is illustrated and designatedgenerally as reference numeral 20. It will be understood and appreciatedby those of ordinary skill in the art that the illustrated medicalinformation computing system environment 20 is merely an example of onesuitable computing environment and is not intended to suggest anylimitation as to the scope of use or functionality of the invention.Neither should the medical information computing system environment 20be interpreted as having any dependency or requirement relating to anysingle component or combination of components illustrated therein.

Embodiments of the present invention may be operational with numerousother general purpose or special purpose computing system environmentsor configurations. Examples of well-known computing systems,environments, and/or configurations that may be suitable for use withthe present invention include, by way of example only, personalcomputers, server computers, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of theabove-mentioned systems or devices, and the like.

Embodiments of the present invention may be described in the generalcontext of computer-executable instructions, such as program modules,being executed by a computer. Generally, program modules include, butare not limited to, routines, programs, objects, components, and datastructures that perform particular tasks or implement particularabstract data types. Embodiments of the present invention may also bepracticed in distributed computing environments where tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules may be located in local and/or remote computer storage mediaincluding, by way of example only, memory storage devices.

With continued reference to FIG. 1, the exemplary computing environment100 includes a general purpose computing device in the form of a server102. Components of the server 102 may include, without limitation, aprocessing unit, internal system memory, and a suitable system bus forcoupling various system components, including database cluster 104, withthe server 102. The system bus may be any of several types of busstructures, including a memory bus or memory controller, a peripheralbus, and a local bus, using any of a variety of bus architectures. Byway of example, and not limitation, such architectures include IndustryStandard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus,Enhanced ISA (EISA) bus, Video Electronic Standards Association (VESA)local bus, and Peripheral Component Interconnect (PCI) bus, also knownas Mezzanine bus.

The server 102 typically includes, or has access to, a variety ofcomputer readable media. Computer readable media can be any availablemedia that may be accessed by server 102, and includes volatile andnonvolatile media, as well as removable and non-removable media. By wayof example, and not limitation, computer readable media may includecomputer storage media and communication media; computer storage mediaexcludes signals per se. Computer storage media may include, withoutlimitation, volatile and nonvolatile media, as well as removable andnonremovable media implemented in any method or technology for storageof information, such as computer readable instructions, data structures,program modules, or other data. In this regard, computer storage mediamay include, but is not limited to, RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile disks (DVDs) or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage, or other magnetic storage device, or any other medium which canbe used to store the desired information and which may be accessed bythe server 102. Communication media typically embodies computer readableinstructions, data structures, program modules, or other data in amodulated data signal, such as a carrier wave or other transportmechanism, and may include any information delivery media. As usedherein, the term “modulated data signal” refers to a signal that has oneor more of its attributes set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared, and other wireless media. Combinations of any of the abovealso may be included within the scope of computer readable media.

The computer storage media discussed above and illustrated in FIG. 1,including database cluster 104, provide storage of computer readableinstructions, data structures, program modules, and other data for theserver 102.

The server 102 may operate in a computer network 106 using logicalconnections to one or more remote computers 108. Remote computers 108may be located at a variety of locations in a medical or researchenvironment, for example, but not limited to, clinical laboratories,hospitals and other inpatient settings, veterinary environments,ambulatory settings, medical billing and financial offices, hospitaladministration settings, home health care environments, and clinicians'offices. Clinicians may include, but are not limited to, a treatingphysician or physicians, specialists such as surgeons, radiologists,cardiologists, and oncologists, emergency medical technicians,physicians' assistants, nurse practitioners, nurses, nurses' aides,pharmacists, dieticians, microbiologists, laboratory experts, geneticcounselors, researchers, veterinarians, students, and the like. Theremote computers 108 may also be physically located in non-traditionalmedical care environments so that the entire health care community maybe capable of integration on the network. The remote computers 108 maybe personal computers, servers, routers, network PCs, peer devices,other common network nodes, or the like, and may include some or all ofthe components described above in relation to the server 102. Thedevices can be personal digital assistants or other like devices.

Exemplary computer networks 106 may include, without limitation, localarea networks (LANs) and/or wide area networks (WANs). Such networkingenvironments are commonplace in offices, enterprise-wide computernetworks, intranets, and the Internet. When utilized in a WAN networkingenvironment, the server 102 may include a modem or other means forestablishing communications over the WAN, such as the Internet. In anetworked environment, program modules or portions thereof may be storedin the server 102, in the database cluster 104, or on any of the remotecomputers 108. For example, and not by way of limitation, variousapplication programs may reside on the memory associated with any one ormore of the remote computers 108. It will be appreciated by those ofordinary skill in the art that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers (e.g., server 102 and remote computers 108) may beutilized.

In operation, a user may enter commands and information into the server102 or convey the commands and information to the server 102 via one ormore of the remote computers 108 through input devices, such as akeyboard, a pointing device (commonly referred to as a mouse), atrackball, or a touch pad. Other input devices may include, withoutlimitation, microphones, satellite dishes, scanners, or the like.Commands and information may also be sent directly from a remotehealthcare device to the server 102. In addition to a monitor, theserver 102 and/or remote computers 108 may include other peripheraloutput devices, such as speakers and a printer.

Although many other internal components of the server 102 and the remotecomputers 108 are not shown, those of ordinary skill in the art willappreciate that such components and their interconnections are wellknown. Accordingly, additional details concerning the internalconstruction of the server 102 and the remote computers 108 are notfurther disclosed herein.

Referring now to FIG. 2, a block diagram is provided illustrating anexemplary computing system 200 in which embodiments of the presentinvention may be employed. Generally, the computing system 200illustrates an environment in which healthcare data may be denormalizedand cached for a user without the user executing a query. The computingsystem 200 may be a comprehensive computing system within a clinicalenvironment similar to the exemplary computing system 20 discussed abovewith reference to FIG. 1. Among other components not shown, thecomputing system 200 generally includes user display devices 212 (e.g.,mobile devices, touch screens or tablet devices, workstations, and thelike), a primed view engine 220, a database 240, and a primed viewdatabase 242 in communication with one another via a network 210. Thenetwork 210 may include, without limitation, one or more local areanetworks (LANs) and/or wide area networks (WANs). Such networkingenvironments are commonplace in offices, enterprise-wide computernetworks, intranets and the Internet. Accordingly, the network 210 isnot further described herein.

It should be understood that any number of user display devices 212and/or primed view engines 220 may be employed in the computing system200 within the scope of embodiments of the present invention. Each maycomprise a single device/interface or multiple devices/interfacescooperating in a distributed environment. For instance, the primed viewengine 220 may comprise multiple devices and/or modules arranged in adistributed environment that collectively provide the functionality ofthe primed view engine 220 described herein. Additionally, othercomponents or modules not shown also may be included within thecomputing system 200.

In some embodiments, one or more of the illustrated components/modulesmay be implemented as stand-alone applications. In other embodiments,one or more of the illustrated components/modules may be implemented viaa user display device 212, the primed view engine 220, or as anInternet-based service. It will be understood by those of ordinary skillin the art that the components/modules illustrated in FIG. 2 areexemplary in nature and in number and should not be construed aslimiting. Any number of components/modules may be employed to achievethe desired functionality within the scope of embodiments hereof.Further, components/modules may be located on and/or shared by anynumber of primed view engines and/or user display devices. By way ofexample only, the primed view engine 220 might be provided as a singlecomputing device (as shown), a cluster of computing devices, or acomputing device remote from one or more of the remaining components.

It should be understood that this and other arrangements describedherein are set forth only as examples. Other arrangements and elements(e.g., machines, interfaces, functions, orders, and groupings offunctions, etc.) can be used in addition to or instead of those shown,and some elements may be omitted altogether. Further, many of theelements described herein are functional entities that may beimplemented as discrete or distributed components or in conjunction withother components, and in any suitable combination and location. Variousfunctions described herein as being performed by one or more entitiesmay be carried out by hardware, firmware, and/or software. For instance,various functions may be carried out by a processor executinginstructions stored in memory.

The primed view engine 220 is configured to, among other things, provideselective denormalization of healthcare data prior to a user executing aquery for data associated with a particular patient. As illustrated, invarious embodiments, the primed view engine 220 includes a trackingcomponent 222, a retrieval component 224, a cache component 228, arefresh component 228, a discharge component 230, a removal component.The primed view engine 220 is communitively coupled to a database 240comprising healthcare data and a primed view database 242. The primedview database 242 may comprise a subset of the healthcare data stored inthe database 240 (e.g., orders and/or results for a select population ofpatients).

The tracking component 222 receives an indication a patient has beenadded to a tracking list. In one embodiment, the tracking componentbuilds the tracking list based on a particular condition associated witha group of patients, a role associated with a clinician treating a groupof patients, and/or a unit associated with a healthcare facility thattreats a group of patients. This allows the tracking list to be tailoredto a particular group of patients, for a particular clinician, or for aparticular unit. In another embodiment, the tracking component buildsthe tracking list based on a schedule of patients that have appointmentson a particular day at a particular facility or with a particularclinician. This allows the tracking list to be automatically populatedeach day with expected patients.

The retrieval component 224 retrieves data for each patient in thetracking list. The data may be limited in time. For example, rather thanretrieving all orders or all results for a patient, only the most recentorders or results may be retrieved. Similarly, only active orders orrecently cancelled orders may be retrieved. The data may further beselected based on a condition associated with the patients, a roleassociated with a clinician, and/or a unit associated with a healthcarefacility. For example, only data that is clinically relevant to thecurrent encounter may be retrieved, such as data associated with aparticular condition. In one embodiment, the tracking list may be builtbased on this condition to retrieve a particular subset of data that isrelevant to that condition. In another embodiment, a particular subsetof data may be retrieved based on data that is relevant to a particularrole associated with a clinician. In another embodiment, a particularsubset of data may be retrieved based on data that is relevant to aparticular unit associated with a healthcare facility.

The cache component 226 caches the data into a primed view. The data maybe cached into primed view before a user initiates a query. In oneembodiment, the data for a particular patient is cached into the primedview before the patient is admitted. In one embodiment, the data for thepatient is cached into the primed view before the patient arrives at thehealthcare facility. In one embodiment, the data for the patient iscached into the primed view when the patient checks in to the healthcarefacility. This allows the clinician to view the most pertinentinformation for each patient during the encounter without being forcedto sort through or query data that is no longer current or relevant.

The refresh component 228 retrieves updated data and refreshes the datawith the updated data in the primed view. The updated data may reflectdata (e.g., an order or result) that has been entered by the clinicianviewing the primed view or by another clinician that has recently had anencounter with the patient. In one embodiment, the primed view isupdated automatically when the updated data is received. In oneembodiment, the primed view is updated when the refresh component 228receives an indication from a clinician to update the data in the primedview.

In one embodiment, the discharge component 230 indicates an appointmenthas ended for the patient or the patient has been discharged. Theremoval component 232 may remove the data for the patient from theprimed view and remove the patient from the tracking list. In oneembodiment, the removal component 232 removes the data for the patientfrom the primed view and removes the patient from the tracking listautomatically when the discharge component 230 indicates the appointmenthas ended or the patient has been discharged. In one embodiment, theremoval component 232 removes the data for the patient from the primedview and removes the patient form the tracking list when an indicationis received from the clinician that indicates the data is no longerneeded in the primed view and the patient is no longer needed in thetracking list.

With reference to FIG. 3, an exemplary flow diagram representative of amethod for populating a custom data mart, in accordance with anembodiment of the present invention is shown and referenced generally bynumeral 300. Method 300 may be implemented using the above-describedexemplary computing system environment (FIG.1). Initially, as shown atstep 310, an indication a patient has been added to a tracking list isreceived. In one embodiment, a schedule of appointments. The schedule ofappointments may be for a particular hour, day, week, and the like.Patients are added to the tracking list based on the schedule ofappointments. This allows the tracking list to be created automatically(e.g., from the schedule) rather than requiring the tracking list to becreated manually (e.g., by a clinician).

The tracking list is determined, at step 310, to be part of a primedview. The primed view comprises a particular format or data. In oneembodiment, a selection of data to include in the primed view isreceived. The selection of data may include defined rows and columnsbased on a condition associated with the patients included in thetracking list. The selection of data may include defined rows andcolumns based on a role associated with a clinician. The selection ofdata may include defined rows and columns based on a unit associatedwith a healthcare facility. This allows the primed view to be tailoredappropriately for the clinician that will view the data.

Data for the patient is retrieved at step 314. The data may be limitedin time so that only the most recent data is retrieved. The data mayalso be limited in scope to conform to the format that comprises theprimed view. In other words, a query is not executed to retrieve alldata for the patient. Rather, the query is limited to retrieve only whatis necessary for the clinician for the current encounter with thepatient.

The data for the patient is cached, at step 316, into the primed view.In one embodiment, the data for the patient is cached into the primedview before the patient is admitted. In one embodiment, the data for thepatient is cached into the primed view before the patient arrives at thehealthcare facility. In one embodiment, the data for the patient iscached into the primed view when the patient checks in to the healthcarefacility. This allows the data in the primed view to be available to theclinician as the clinician attends to, treats, or interacts with thepatient.

In one embodiment, an indication a new order or result is available forat least one patient in the tracking list is received. The order orresult may be entered by the clinician viewing the primed view or byanother clinician that has recently had an encounter with the patient.The indication alerts the clinician that the primed view needs to berefreshed. In one embodiment, the updated data is retrieved for the atleast one patient. In one embodiment, the updated data is cached intothe primed view. This allows the clinician to view the primed view withthe updated data included. In one embodiment, the primed view is updatedautomatically when the updated data is received. In one embodiment, theprimed view is updated manually by the clinician such as upon theclinician being alerted that a new order or result is available,allowing the clinician to manually select for the updated data to beretrieved and cached into the primed view.

In one embodiment, an indication the patient has been discharged isreceived. In one embodiment, an indication the appointment is completefor the patient is received. The data for the patient may be removedfrom the primed view and the patient may be removed from the trackinglist. In one embodiment, the data for the patient may be removedautomatically from the primed view when the indication is received.Similarly, the patient may be removed from the tracking list when theindication is received. In another embodiment, the data for the patientmay not be removed until an indication is received from the clinicianthat indicates the data is no longer needed in the primed view.Similarly, the patient may be removed from the tracking list when anindication is received from the clinician that indicates the patient isno longer needed in the tracking list (i.e., the appointment is completeor the patient has been discharged and the clinician has completedcharting for the patient).

With reference to FIG. 4, an exemplary flow diagram representative of amethod for denormalizing healthcare data, in accordance with anembodiment of the present invention is shown and referenced generally bynumeral 400. Method 400 may be implemented using the above-describedexemplary computing system environment (FIG. 1). Initially, as shown atstep 410, a tracking list of patients is prepared. The tracking list isbased on a schedule of appointments.

Data is retrieved for each patient in the tracking list at step 412. Thedata is limited in time and selected based on a condition associatedwith the patients, a role associated with a clinician, and/or a unitassociated with a healthcare facility. Retrieving data that is limitedin time allows the clinician to view the most recent data (e.g., ordersand/or results) without needing to scroll through or review data fromevery encounter for each patient. Selecting the data based on acondition allows only the most relevant data to be retrieved. Forexample, a clinician may be treating patients that have a particularcondition. Only certain data for this condition may actually be relevantto the clinician. Similarly, certain data may only be relevant to aclinician with a particular role or to a particular unit of thehealthcare facility. Rather than retrieving all available data, onlydata that is relevant to the treatment of the patient for the currentencounter is retrieved.

At step 414, the data is cached into a primed view. The primed view isavailable to the clinician without the clinician requesting the data. Inother words, the data may be automatically retrieved based on thetracking list (e.g., daily schedule of appointments, weekly schedule ofappointments, etc.). This allows the most recent and relevant data to beavailable for each patient on the tracking list without the clinicianneeding to request any information.

An indication is received, at step 416, that updated data is availablefor one or more patients. For example, data may have been updated thatis not yet available in the primed view. An order may have been placedby the clinician or another clinician. Similarly, results may beavailable that were not available when the data was initially cached inthe primed view. The indication may alert the clinician that more recentdata is available. At step 418, the data is refreshed with the updateddata in the primed view. In one embodiment, the data may be refreshedautomatically, such as after a particular time has elapsed after theindication is received or in real-time when the data is available.

In one embodiment, an indication is received that the appointment isover for a patient. The data may be removed for the patient from theprimed view. In one embodiment, the data is automatically removed whenthe patient checks out from the appointment or is discharged from thefacility. In one embodiment, the data is removed when the clinicianmanually removes the data. In one embodiment, the patient is removedfrom the tracking list. In one embodiment, the patient is automaticallyremoved from the tracking list when the patient checks out from theappointment or is discharged from the facility. In one embodiment, thepatient is manually removed from the tracking list by the clinician. Inone embodiment, removing the patient from the tracking list removes thedata for the patient from the primed view.

As can be understood, the present invention provides systems, methods,and user interfaces for selective denormalization of healthcare data.The present invention has been described in relation to particularembodiments, which are intended in all respects to be illustrativerather than restrictive. Alternative embodiments will become apparent tothose of ordinary skill in the art to which the present inventionpertains without departing from its scope.

From the foregoing, it will be seen that this invention is one welladapted to attain all the ends and objects set forth above, togetherwith other advantages which are obvious and inherent to the system andmethod. It will be understood that certain features and subcombinationsare of utility and may be employed without reference to other featuresand subcombinations. This is contemplated and within the scope of theclaims.

What is claimed is:
 1. Computer storage media having computer-executableinstructions embodied thereon, that when executed, perform a method offacilitating selective denormalization of healthcare data, the methodcomprising: receiving an indication a patient has been added to atracking list; determining the tracking list is associated with a primedview; retrieving data for the patient; and caching the data for thepatient into the primed view before a clinician requests the data. 2.The media of claim 1, further comprising receiving a schedule ofappointments.
 3. The media of claim 2, further comprising adding thepatient to the tracking list based on the schedule of appointments. 4.The media of claim 3, wherein the data for the patient is cached intothe primed view before the patient is admitted.
 5. The media of claim 1,further comprising receiving an indication a new order or result isavailable for at least one patient in the tracking list.
 6. The media ofclaim 5, further comprising receiving updated data for the at least onepatient.
 7. The media of claim 6, further comprising caching the updateddata into the primed view.
 8. The media of claim 1, further comprisingreceiving an indication the patient has been discharged.
 9. The media ofclaim 8, further comprising removing the data for the patient from theprimed view.
 10. The media of claim 9, further comprising removing thepatient from the tracking list.
 11. The media of claim 10, furthercomprising retrieving a selection of data to include in the primed view.12. The media of claim 11, wherein the selection of data is based on acondition associated with the patient.
 13. The media of claim 11,wherein the selection of data is based on a role associated with aclinician.
 14. The media of claim 11, wherein the selection of data isbased on a unit associated with a healthcare facility.
 15. Computerstorage media having computer-executable instructions embodied thereon,that when executed, perform a method of facilitating selectivedenormalization of healthcare data, the method comprising: preparing atracking list of patients based on a schedule of appointments;retrieving data for each patient in the tracking list, the data limitedin time and selected based on a condition associated with the patients,a role associated with a clinician, a configurable definition, and/or aunit associated with a healthcare facility; caching the data into aprimed view, the primed view available to the clinician without theclinician requesting the data; receiving an indication updated data isavailable for one or more patients; and refreshing the data with theupdated data in the primed view.
 16. The media of claim 15, furthercomprising receiving an indication the appointment is over for apatient.
 17. The media of claim 16, further comprising removing the datafor the patient from the primed view.
 18. The media of claim 17, furthercomprising removing the patient from the tracking list.
 19. A computersystem for facilitating the selective denormalization of healthcaredata, the computer system comprising one or more processors coupled to acomputer hardware storage medium, the computer hardware storage mediumhaving stored thereon a plurality of computer software componentsexecutable by the one or more processors, the computer softwarecomponents comprising: a tracking component that receives an indicationa patient has been added to a tracking list; a retrieval component thatretrieves data for each patient in the tracking list, the data limitedin time and selected based on a condition associated with the patients,a role associated with a clinician, a configurable definition, and/or aunit associated with a healthcare facility; a cache component thatcaches the data into a primed view, the primed view provided before auser initiates a query; and a refresh component that retrieves updateddata and refreshes the data with the updated data in the primed view.20. The system of claim 19, further comprising: a discharge componentthat indicates an appointment has ended for the patient or the patienthas been discharged; a removal component that removes the data for thepatient from the primed view and removes the patient from the trackinglist.